SGI Varsity Update 1998 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Varsity Update 1998 August / SGI Varsity Update 1998 August.iso / docs / relnotes / pcp / ch2.z / ch2

Wrap

Text File | 1998-07-29 | 50KB | 1,322 lines

- 1 - 2. _I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n This chapter lists supplemental information to the _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g _G_u_i_d_e. The information listed here is product- and release-specific; use it with the _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g _G_u_i_d_e to install this product. Additional information concerning PCP installation and post-installation customization may be found in the Insight book _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _U_s_e_r'_s _a_n_d _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e that is distributed with the images. 2.1 _P_e_r_f_o_r_m_a_n_c_e__C_o_-_P_i_l_o_t__S_u_b_s_y_s_t_e_m_s The _p_c_p product includes these subsystems: _p_c_p._b_o_o_k_s._P_C_P__P_G The _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e, an Insight book. _p_c_p._b_o_o_k_s._P_C_P__U_A_G The _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _U_s_e_r_s'_s _a_n_d _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e, an Insight book. _p_c_p._b_o_o_k_s._P_m_C_h_a_r_t_H_e_l_p SGIHelp book for the ppppmmmmcccchhhhaaaarrrrtttt(1) application from _p_c_p._s_w._m_o_n_i_t_o_r. _p_c_p._b_o_o_k_s._P_m_V_i_e_w_H_e_l_p SGIHelp book for the ppppmmmmvvvviiiieeeewwww(1) application from _p_c_p._s_w._m_o_n_i_t_o_r. _p_c_p._m_a_n._p_a_g_e_s Manual pages for the binaries and libraries. _p_c_p._m_a_n._r_e_l_n_o_t_e_s These release notes. _p_c_p._m_a_n._t_u_t_o_r_i_a_l An HTML tutorial that highlights the features and services of PCP. _p_c_p._s_w._b_a_s_e Executable programs, libraries, scripts and configuration files that are required for every PCP deployment. Also, the header files required to compile C (or C++) programs that use the Performance Metrics API (PMAPI) supported by the Performance Co-Pilot. - 2 - You need to install this subsystem if you wish to use the Performance Co-Pilot in either monitor or collector configurations, or if you wish to develop new programs using the PMAPI, or compile any of the demonstration programs that use the PMAPI. _p_c_p._s_w._c_i_s_c_o The optional CCCCiiiissssccccoooo Performance Metrics Domain Agent (PMDA) collects performance metrics characterizing traffic through one or more Cisco routers. This subsystem must be installed on each collector configuration from which Cisco metrics are to be exported. _p_c_p._s_w._c_o_m_p_a_t Old versions of the PCP libraries and headers. May be required for compatibility with older binaries and PMDAs from earlier PCP releases and PCP add-on products that are not based on PCP 2.0 or later. _p_c_p._s_w._d_e_m_o Source code and annotated examples for some PCP tools, some sample programs and optional demonstration PMDAs. The latter provide a basis for the development of new PMDAs to incorporate additional performance metrics from site- specific and application-specific domains into the PCP framework. The sample programs provide a basis for the development of new clients to provide either generic, or site-specific and/or application-specific processing and analysis of performance metrics delivered via the PCP framework. _p_c_p._s_w._e_n_v_i_r_o_n The optional EEEEnnnnvvvviiiirrrroooonnnn PMDA collects performance metrics from the environmental monitor on a Challenge or Onyx system. This subsystem must be installed on each collector configuration from which environ metrics are to be exported. _p_c_p._s_w._h_o_t_p_r_o_c The optional hhhhoooottttpppprrrroooocccc PMDA may be configured to export pppprrrrooooccccffffssss(4) performance metrics for those processes that satisfy local selection criteria, - 3 - e.g. burning lots of CPU cycles, excessive system calls, owned by the user ``mary'', etc. This subsystem must be installed on each collector configuration from which hotproc metrics are to be exported. _p_c_p._s_w._m_a_i_l_q The optional mmmmaaaaiiiillllqqqq PMDA may be configured to export performance metrics describing the state of the sssseeeennnnddddmmmmaaaaiiiillll(1) mail queue. This subsystem must be installed on each collector configuration from which mailq metrics are to be exported. _p_c_p._s_w._m_o_n_i_t_o_r The components for a PCP monitor configuration, including all of the tools for display, visualization and automated reasoning about performance data. For a PCP collector-only configuration, installation of this subsystem is not required. _p_c_p._s_w._s_h_p_i_n_g The optional sssshhhhppppiiiinnnngggg PMDA may be configured to export performance metrics that measure quality of service and service availability for any service that can be exercised from an interactive shell. The PMDA periodically runs and times commands using sssshhhh(1). This subsystem must be installed on each collector configuration from which shping metrics are to be exported. _p_c_p._s_w._s_u_m_m_a_r_y The optional ssssuuuummmmmmmmaaaarrrryyyy PMDA may be configured to export performance metrics computed from other performance metrics on one or more hosts. This subsystem must be installed on each collector configuration from which summary metrics are to be exported. _p_c_p._s_w._t_r_a_c_e The optional ttttrrrraaaacccceeee PMDA may be used to export performance metrics collected from applications instrumented with the _l_i_b_p_c_p__t_r_a_c_e library, or observations generated by the ppppmmmmttttrrrraaaacccceeee(1) - 4 - application. This subsystem must be installed on each collector configuration from which trace metrics are to be exported. _p_c_p._s_w_6_4._b_a_s_e 64-bit libraries that may be installed on 32-bit IRIX platforms for PCP developers. Note that on 64-bit IRIX platforms all required libraries (32-bit and 64-bit) are installed from _p_c_p._s_w._b_a_s_e and so it is expected that _p_c_p._s_w_6_4._b_a_s_e will nnnnooootttt be installed on most systems. _p_c_p._s_w_6_4._c_o_m_p_a_t 64-bit compatibility libraries that may be installed on 32-bit IRIX platforms for PCP developers. Note that on 64-bit IRIX platforms all required compatibility libraries (32-bit and 64-bit) are installed from _p_c_p._s_w._c_o_m_p_a_t and so it is expected that _p_c_p._s_w_6_4._c_o_m_p_a_t will nnnnooootttt be installed on most systems. 2.2 _S_u_b_s_y_s_t_e_m__R_e_-_s_t_r_u_c_t_u_r_i_n_g__f_r_o_m__P_C_P__1_._x Some re-arrangement of the subsystem structure for the PCP product occurred between versions 1.x and version 2.0, most notably the splitting of _p_c_p into _p_c_p__e_o_e and _p_c_p. The table below describes the relationship between the changed subsystems in the two versions. ______________________________________________ Corresponding PCP 1.x Subsystem Subsystem(s) for PCP 2.0 ____________________________________________________________________________________________ pcp.sw.collector pcp_eoe.sw.eoe pcp.sw.base ______________________________________________ pcp.sw.eoe pcp.sw.base pcp_eoe.sw.eoe ______________________________________________ pcp.sw.monitor pcp_eoe.sw.monitor pcp.sw.monitor ______________________________________________ pcp.man.pages pcp_eoe.man.pages pcp.man.pages ______________________________________________ ||||||||||||| ||||||||||||| ||||||||||||| - 5 - 2.3 _P_e_r_f_o_r_m_a_n_c_e__C_o_-_P_i_l_o_t__S_u_b_s_y_s_t_e_m__D_i_s_k__S_p_a_c_e__R_e_q_u_i_r_e_m_e_n_t_s This section lists the _p_c_p subsystems (and their sizes). If you are installing this product for the first time, the subsystems marked ``default'' are the ones that are installed if you use the ``go'' menu item. To install a different set of subsystems, use the ``install,'' ``remove,'' ``keep,'' and ``step'' commands in iiiinnnnsssstttt to customize the list of subsystems to be installed, then select the ``go'' menu item. Note: The listed subsystem sizes are approximate. Refer to the _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g _G_u_i_d_e for information on finding exact sizes. Subsystem Name Subsystem Size (Kbytes) _p_c_p._b_o_o_k_s._P_C_P__P_G 1000 _p_c_p._b_o_o_k_s._P_C_P__U_A_G 2000 _p_c_p._b_o_o_k_s._P_m_C_h_a_r_t_H_e_l_p 550 _p_c_p._b_o_o_k_s._P_m_V_i_e_w_H_e_l_p 400 _p_c_p._m_a_n._p_a_g_e_s 650 _p_c_p._m_a_n._r_e_l_n_o_t_e_s (default) 50 _p_c_p._m_a_n._t_u_t_o_r_i_a_l 2000 _p_c_p._s_w._b_a_s_e (default) 550 _p_c_p._s_w._c_i_s_c_o 80 _p_c_p._s_w._c_o_m_p_a_t 1650 _p_c_p._s_w._d_e_m_o 300 _p_c_p._s_w._e_n_v_i_r_o_n 40 _p_c_p._s_w._h_o_t_p_r_o_c 150 _p_c_p._s_w._m_a_i_l_q 30 _p_c_p._s_w._m_o_n_i_t_o_r 3100 _p_c_p._s_w._s_h_p_i_n_g 50 _p_c_p._s_w._s_u_m_m_a_r_y 40 _p_c_p._s_w._t_r_a_c_e 150 _p_c_p._s_w_6_4._b_a_s_e 60 _p_c_p._s_w_6_4._c_o_m_p_a_t 1000 - 6 - 2.4 _I_n_s_t_a_l_l_a_t_i_o_n__M_e_t_h_o_d All of the subsystems for Performance Co-Pilot can be installed using IRIX. You do not need to use the miniroot. Refer to the _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g _G_u_i_d_e for complete installation instructions. 2.5 _P_r_e_r_e_q_u_i_s_i_t_e_s The split of _p_c_p into _p_c_p__e_o_e and _p_c_p is accompanied by some cross-product dependencies, namely: i. through chained dependencies on _p_c_p._s_w._b_a_s_e most subsystems in _p_c_p require prior installation of _p_c_p__e_o_e._s_w._e_o_e. ii. _p_c_p._s_w._m_o_n_i_t_o_r requires prior installation of _p_c_p__e_o_e._s_w._m_o_n_i_t_o_r and since this is not a default subsystem you may have to go back to the _p_c_p__e_o_e distribution to install _p_c_p__e_o_e._s_w._m_o_n_i_t_o_r before proceeding with the _p_c_p._s_w._m_o_n_i_t_o_r installation Due to packaging and file location changes, there are some versions of PCP add-on products (as per the table below) that are incompatible with PCP 2.0 and should be removed before PCP 2.0 is installed. Once PCP 2.0 has been installed, the new versions of the corresponding add-on products should be re-installed with iiiinnnnsssstttt. _____________________________________________________ PCP Add-on Version to Remove Version to Install Product Before PCP 2.0 After PCP 2.0 _____________________________________________________ PCPWEB 1.0 1.1 _____________________________________________________ |||| |||| |||| |||| For example, # versions remove pcp_web # inst ... PCP 2.0 # inst ... PCPWEB 1.1 If you are upgrading an existing PCP installation, and you have any of the PCP add-on products in the table below you mmmmuuuusssstttt install the _p_c_p._s_w._c_o_m_p_a_t subsystem to provide compatible versions of the PCP libraries so that the applications and PMDAs in the add-on products will continue to operate. - 7 - ___________________________________ AAAAdddddddd----oooonnnn PPPPrrrroooodddduuuucccctttt VVVVeeeerrrrssssiiiioooonnnn((((ssss)))) ___________________________________ SC4-FSAFE-PCP 1.2 or earlier SC4-PCPARRAY 1.0 SC4-PCPINFMX7 1.0 SC4-PCPORA 1.2 or earlier SC4-PCPORIGIN 1.1 or earlier SC4-PCPSYB10 1.0 SC4-PCPWEB 1.1.2 or earlier ___________________________________ ||||||||| ||||||||| ||||||||| _p_c_p._s_w._d_e_m_o contains C source files that need to be compiled. To compile these example programs prior installation of the following subsystems is required: _d_e_v._h_d_r._l_i_b, _d_e_v._s_w._l_i_b, _c__d_e_v._s_w._c, _c_o_m_p_i_l_e_r__d_e_v._h_d_r._l_i_b, _c_o_m_p_i_l_e_r__d_e_v._s_w._b_a_s_e, _c_o_m_p_i_l_e_r__d_e_v._s_w._l_d and _c_o_m_p_i_l_e_r__d_e_v._s_w._l_i_b. However, as the _p_c_p._s_w._d_e_m_o subsystem includes a number of other examples that do not require compilation, these prerequisites are not mandated in the PCP images. The collector and monitor functionality of the PCP product require the installation of separate collector and monitor software licenses to operate, and installation of the software will be expedited if the license(s) are installed before the PCP installation commences. Refer to chapter 7 of these release notes for the license installation procedure. If Performance Co-Pilot is to be installed in a ccccoooolllllllleeeeccccttttoooorrrr ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn then the _l_i_b_i_r_i_x_p_m_d_a._s_o library is required to export performance metrics from IRIX. The following table describes where to locate the appropriate version of _l_i_b_i_r_i_x_p_m_d_a._s_o. _________________________________________________ IRIX Source of _l_i_b_i_r_i_x_p_m_d_a._s_o __________________________________________________________________________________________________ /_u_s_r/_p_c_p/_l_i_b/_l_i_b_i_r_i_x_p_m_d_a._s_o is shipped as part of the IRIX _p_c_p__e_o_e._s_w._e_o_e subsystem. 6.5 _________________________________________________ The files /_u_s_r/_p_c_p/_l_i_b/_m_i_p_s_*./_l_i_b_i_r_i_x_p_m_d_a._s_o should be installed from the IRIX patch ppppaaaattttcccchhhhSSSSGGGG0000000000002222888822228888....eeeeooooeeee____sssswwww....ppppeeeerrrrffff that is included with the Performance Co-Pilot distribution. This patch updates the IRIX 6.4 _e_o_e._s_w._p_e_r_f subsystem. 6.4 _________________________________________________ The files 6.3 _________________________________________________ |||||||||||||| |||||||||||||| |||||||||||||| - 8 - /_u_s_r/_p_c_p/_l_i_b/_m_i_p_s_*./_l_i_b_i_r_i_x_p_m_d_a._s_o should be installed from the IRIX patch ppppaaaattttcccchhhhSSSSGGGG0000000000002222888822227777....eeeeooooeeee____sssswwww....ppppeeeerrrrffff that is included with the Performance Co-Pilot distribution. This patch updates the IRIX 6.3 _e_o_e._s_w._p_e_r_f subsystem. _________________________________________________ The files /_u_s_r/_p_c_p/_l_i_b/_m_i_p_s_*./_l_i_b_i_r_i_x_p_m_d_a._s_o should be installed from the IRIX patch ppppaaaattttcccchhhhSSSSGGGG0000000000002222888822226666....eeeeooooeeee____sssswwww....ppppeeeerrrrffff that is included with the Performance Co-Pilot distribution. This patch updates the IRIX 6.2 _e_o_e._s_w._p_e_r_f subsystem. 6.2 _________________________________________________ /_u_s_r/_l_i_b/_p_c_p/_l_i_b_i_r_i_x_p_m_d_a._s_o should be installed from the IRIX patch ppppaaaattttcccchhhhSSSSGGGG0000000000002222888822225555....eeeeooooeeee2222____sssswwww....ppppeeeerrrrffff included with the Performance Co-Pilot distribution. This patch updates the IRIX 5.3 _e_o_e_2._s_w._p_e_r_f subsystem. 5.3 _________________________________________________ ||||||||||||||||||||| ||||||||||||||||||||| ||||||||||||||||||||| For hosts in a PCP mmmmoooonnnniiiittttoooorrrr----oooonnnnllllyyyy ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn which are upgraded to PCP 2.0 and used to monitor remote PCP collector hosts runnning PCP 1.x, the IRIX metrics must appear in the local Performance Metrics Name Space (PMNS) on the PCP monitor host. For IRIX 6.5 systems, the IRIX metrics are included in the PMNS from the _p_c_p__e_o_e._s_w._e_o_e subsystem, so there is no issue. For systems running earlier IRIX releases, the IRIX metrics are included with the _l_i_b_i_r_i_x_p_m_d_a patches, as described in the table above. The work around then, even if ppppmmmmccccdddd(1) is not running, is to install the appropriate _l_i_b_i_r_i_x_p_m_d_a patch on the PCP monitor system, and then run the following commands as rrrrooooooootttt: # cd /var/pcp/pmns # ./Rebuild -du There is no issue if the remote PCP collector hosts are running PCP 2.0 as the distributed name space services will be used in preference to any local PMNS. The _p_c_p__e_o_e._b_o_o_k_s.* subsystems require the _i_n_s_i_g_h_t._s_w images (IRIX 5.3) or the _i_n_s_i_g_h_t__b_a_s_e._s_w images (IRIX 6.2 or later) to be installed. - 9 - The _p_c_p__e_o_e._s_w._m_o_n_i_t_o_r utilities require dynamic shared libraries from the subsystems: _V_i_e_w_K_i_t__e_o_e._s_w._b_a_s_e and _i_n_v_e_n_t_o_r__e_o_e._s_w._i_n_v_e_n_t_o_r (version 2.1 or later). If the Performance Metrics Collector Daemon (PMCD) is already running on the system to which the new installation is going to be applied, then you must terminate ppppmmmmccccdddd before starting the installation. Similarly, any instance of the ppppmmmmllllooooggggggggeeeerrrr utility should be terminated. For example, use the following commands as rrrrooooooootttt: # /etc/init.d/pcp stop # killall -INT pmlogger This is necessary because the subsystems to be installed include new versions of shared libraries (DSOs) that may be used by these PCP utilities. 2.6 _C_o_n_c_u_r_r_e_n_t__I_R_I_X__U_p_g_r_a_d_e_s If you have PCP 1.x installed and are concurrently upgrading IRIX and PCP, or have PCP 2.0 installed and are upgrading IRIX, then there are some complex product interdependencies that are best addressed by following the recommended procedures below. IIIIRRRRIIIIXXXX 5555....3333 aaaannnndddd PPPPCCCCPPPP 1111....xxxx ttttoooo IIIIRRRRIIIIXXXX 6666....2222 aaaannnndddd PPPPCCCCPPPP 2222....0000 1. If the system is configured as a PCP ccccoooolllllllleeeeccccttttoooorrrr, then force the removal of _p_c_p._s_w._c_o_l_l_e_c_t_o_r, i.e. # versions -F remove pcp.sw.collector 2. Upgrade IRIX. 3. Install _p_c_p__e_o_e and upgrade _p_c_p from the PCP 2.0 CD. IIIIRRRRIIIIXXXX 5555....3333 aaaannnndddd PPPPCCCCPPPP 2222....0000 ttttoooo IIIIRRRRIIIIXXXX 6666....2222 aaaannnndddd PPPPCCCCPPPP 2222....0000 In this case it is possible to perform both upgrades concurrently, but this involves a fair degree of CD swapping and delaying the conflict resolutions. A simpler solution is: 1. Force the removal of _p_c_p and _p_c_p__e_o_e, but none of the add-ons products which depend on _p_c_p or _p_c_p__e_o_e (e.g. _p_c_p__w_e_b or _p_c_p__o_r_a_7) as these dependencies will be again satisfied once PCP 2.0 is installed, i.e. # versions -F remove pcp pcp_eoe - 10 - 2. Upgrade IRIX. 3. Re-install _p_c_p__e_o_e and _p_c_p from the PCP 2.0 CD. For information about upgrading IRIX to IRIX 6.5, please also refer to the release notes for _p_c_p__e_o_e in the IRIX 6.5 distribution. IIIIRRRRIIIIXXXX 6666....2222 aaaannnndddd PPPPCCCCPPPP 1111....xxxx ttttoooo IIIIRRRRIIIIXXXX 6666....5555 aaaannnndddd PPPPCCCCPPPP 2222....0000 IIIIRRRRIIIIXXXX 5555....3333 aaaannnndddd PPPPCCCCPPPP 1111....xxxx ttttoooo IIIIRRRRIIIIXXXX 6666....5555 aaaannnndddd PPPPCCCCPPPP 2222....0000 IIIIRRRRIIIIXXXX 6666....2222 aaaannnndddd PPPPCCCCPPPP 2222....0000 ttttoooo IIIIRRRRIIIIXXXX 6666....5555 aaaannnndddd PPPPCCCCPPPP 2222....0000 IIIIRRRRIIIIXXXX 5555....3333 aaaannnndddd PPPPCCCCPPPP 2222....0000 ttttoooo IIIIRRRRIIIIXXXX 6666....5555 aaaannnndddd PPPPCCCCPPPP 2222....0000 In all cases, use the PCP 2.0 CD concurrent with the IRIX CDs to install or upgrade _p_c_p__e_o_e and upgrade _p_c_p at the same time that all IRIX upgrades are done. Note that the _p_c_p__e_o_e subsystem is part of IRIX and is on the Foundation-2 CD, whereas the _p_c_p subsystems for IRIX 6.5 are on the PCP 2.0 CD. Concurrent installations are best performed using the ooooppppeeeennnn command to select products from multiple CDs. For further details, refer to the _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g _G_u_i_d_e. 2.7 _P_o_s_t_-_I_n_s_t_a_l_l_a_t_i_o_n__P_r_o_c_e_d_u_r_e_s If the Performance Metrics Collector Daemon (PMCD) is to be started (i.e. this system is to be a PCP collector) use the following commands as rrrrooooooootttt: # chkconfig pmcd on # chkconfig pmlogger on # /etc/init.d/pcp start Refer to the ppppmmmmccccdddd(1) man page for more details. Note that ``chkconfig pmlogger on'' is only required if you wish to launch the primary ppppmmmmllllooooggggggggeeeerrrr instance in conjunction with ppppmmmmccccdddd - refer to the ppppmmmmllllooooggggggggeeeerrrr(1) and ccccrrrroooonnnn....ppppmmmmcccchhhheeeecccckkkk(1) man pages for more details. The cccchhhhkkkkccccoooonnnnffffiiiigggg option for ppppmmmmllllooooggggggggeeeerrrr defaults to ``off''. For IRIX 6.5, the cccchhhhkkkkccccoooonnnnffffiiiigggg option for ppppmmmmccccdddd defaults to ``on'', otherwise it defaults to ``off''. - 11 - 2.8 _C_o_m_p_a_t_i_b_i_l_i_t_y PCP 2.0 involves some evolutionary changes that may affect some PCP upgrades and PCP add-on products. The following points highlight these dependencies and suggest work arounds for minor incompatibility issues. 1. For upgrades of hosts with a PCP collector configuration, some PMDAs from the _p_c_p product that have been installed (using the PMDA _I_n_s_t_a_l_l scripts to integrate the PMDA with ppppmmmmccccdddd(1)) may have to be re- installed. The symptom is usually a failure to start the PMDA, or an error when accessing the PMDA's help text files, as reported in the /_v_a_r/_a_d_m/_p_c_p_l_o_g/*._l_o_g files. The known PMDAs in this category are: cccciiiissssccccoooo, eeeennnnvvvviiiirrrroooonnnn, ssssaaaammmmpppplllleeee, ssssiiiimmmmpppplllleeee, ssssuuuummmmmmmmaaaarrrryyyy and ttttrrrriiiivvvviiiiaaaallll. To correct the problem, re-run the _I_n_s_t_a_l_l script as rrrrooooooootttt, e.g. # cd /var/pcp/pmdas/cisco # ./Install 2. For hosts in a PCP collector configuration with the SC4-PCPORA product installed, the PMDA _I_n_s_t_a_l_l scripts for the ORACLE PMDAs will choose the wrong versions of the PCP libraries when relinking the PMDA binary, e.g. _l_i_b_p_c_p._s_o._2 rather than _l_i_b_p_c_p._s_o._1 Ensure _p_c_p._s_w._c_o_m_p_a_t is installed, then in both the /_u_s_r/_p_c_p/_p_m_d_a_s/_o_r_a_c_l_e_7 and /_u_s_r/_p_c_p/_p_m_d_a_s/_o_r_a_p_i_n_g directories, edit the file _M_a_k_e_f_i_l_e._o_r_a and replace ----llllppppccccpppp by ----llll////uuuussssrrrr////lllliiiibbbb////lllliiiibbbbppppccccpppp....ssssoooo....1111 Then re-install the PMDA(s) using the _I_n_s_t_a_l_l script in the PMDA directory. 3. For upgraded hosts with a collector configuration, ppppmmmmccccdddd(1) chooses the new protocols by default when starting a PMDA. If the PMDA is from an earlier add- on product (which requires _p_c_p._s_w._c_o_m_p_a_t to be installed), then PMCD will timeout waiting for a new protocol exchange and then assume this is an old PMDA. When this occurs, PMCD may take a little longer to start up, and messages will appear in /_v_a_r/_a_d_m/_p_c_p_l_o_g/_p_m_c_d._l_o_g of the form: [date] pmcd(...) Warning: pduread: timeout (after 3.000 sec) on fd=... pmcd: no version exchange with PMDA ...: assuming PCP 1.x PMDA. These messages are benign and the PMDA will function correctly. Subsequent releases of the PCP add-on products will contain new PMDAs built on the PCP 2.0 - 12 - protocols, at which time the messages will go away. To determine if a PMDA is using the old protocols, locate the name of the PMDA from /_e_t_c/_p_m_c_d._c_o_n_f and then use the option ----DDDDllll to eeeellllffffdddduuuummmmpppp(1) on the PMDA binary - if the PMDA is linked with Version sgi1111.0 of _l_i_b_p_c_p._s_o rather than Version sgi2222.0, then it is using the old protocols. In the example below _p_m_d_a_w_e_b_l_o_g is using the old protocols and _p_m_d_a_m_a_i_l_q is using the new protocols. $ elfdump -Dl /var/pcp/pmdas/weblog/pmdaweblog ... [INDEX] ... Name Version [1] ... libpcp_pmda.so sgi1.0 [2] ... libpcp.so.1 sgi1.0 [3] ... libgen.so sgi1.0 [4] ... libc.so.1 sgi1.0 $ elfdump -Dl /var/pcp/pmdas/weblog/pmdamailq ... [INDEX] ... Name Version [1] ... libpcp_pmda.so sgi2.0 [2] ... libpcp.so.2 sgi2.0 [3] ... libc.so.1 sgi1.0 4. The PMDA _I_n_s_t_a_l_l and _R_e_m_o_v_e scripts for the SC4- PCPSYB10 product assume the PMDA log files will be created in /_v_a_r/_t_m_p, however for PCP 1.2.1 and later these files will be created in /_v_a_r/_a_d_m/_p_c_p_l_o_g by default. When running the PMDA _I_n_s_t_a_l_l or _R_e_m_o_v_e scripts for ssssyyyybbbb11110000 or ssssyyyybbbbppppiiiinnnngggg PMDAs, use the following steps: +o Login as rrrrooooooootttt. +o # /etc/init.d/pcp stop # PCP_LOGDIR=/var/tmp; export PCP_LOGDIR +o Install or Remove, as per the instructions for the PMDA. +o # unset PCP_LOGDIR # /etc/init.d/pcp start - 13 - 2.9 _C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s The post-installation and PCP customization tasks are fully described in the _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _U_s_e_r'_s _a_n_d _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e Insight book. The notes in this section serve as a summary. You may need to edit some configuration files to complete the PCP installation, configuration and customization. If you are reinstalling PCP or upgrading an earlier PCP installation, any existing configuration will be retained, and any new default configuration files will be installed with a ....NNNN file suffix. +o /_e_t_c/_p_m_c_d._c_o_n_f - this file specifies which Performance Metrics Domain Agents (PMDAs) shall be available. Refer to the ppppmmmmccccdddd(1) man page for further details. If you are upgrading a Performance Co-Pilot installation, you may need to re-install any optional PMDAs. The procedure for doing this is covered in the last section of this chapter. +o /_e_t_c/_c_o_n_f_i_g/_p_m_c_d - this file controls whether the Performance Metrics Collector Daemon (PMCD) is run as part of the system boot procedure. Refer to the ppppmmmmccccdddd(1) man page for further details. +o /_e_t_c/_c_o_n_f_i_g/_p_m_c_d._o_p_t_i_o_n_s - command-line options for the automatic startup of the PMCD. Refer to the ppppmmmmccccdddd(1) man page for further details. +o /_e_t_c/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r - this file controls whether the primary instance of ppppmmmmllllooooggggggggeeeerrrr is run as part of the system boot procedure. Refer to the ppppmmmmllllooooggggggggeeeerrrr(1) man page for further details. +o /_e_t_c/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r._o_p_t_i_o_n_s - command-line options for the automatic startup of the primary ppppmmmmllllooooggggggggeeeerrrr instance. Refer to the ppppmmmmllllooooggggggggeeeerrrr(1) man page for further details. +o /_v_a_r/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r/_c_o_n_f_i_g._d_e_f_a_u_l_t - this file specifies the performance metrics to be logged and frequency of logging by the primary logger. Refer to the ppppmmmmllllooooggggggggeeeerrrr(1) man page for further details. If you are upgrading a Performance Co-Pilot 1.0 installation, and you wish to retain the existing configuration file /_u_s_r/_l_i_b/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r._c_o_n_f_i_g for the primary logger, you should do the following as rrrrooooooootttt: - 14 - # cd /usr/lib/pcp/config # mv pmlogger.config /var/pcp/config/pmlogger/config.default If you are upgrading a Performance Co-Pilot 1.1 installation, and you wish to retain the existing configuration file /_u_s_r/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r._c_o_n_f_i_g for the primary logger, you should do the following as rrrrooooooootttt: # cd /usr/pcp/config # mv pmlogger.config /var/pcp/config/pmlogger/config.default Otherwise you may wish to remove the old /_u_s_r/_l_i_b/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r._c_o_n_f_i_g and/or /_u_s_r/_p_c_p/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r._c_o_n_f_i_g files. +o /_v_a_r/_p_c_p/_p_m_n_s - this directory contains both a machine friendly (/_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t._b_i_n) and human readable format (all other files) of the default Performance Metrics Name Space (PMNS). Refer to the ppppmmmmnnnnssss(4) and ppppmmmmnnnnssssccccoooommmmpppp(1) man pages for further details. If you are upgrading a Performance Co-Pilot 1.0 installation, it is recommended that you remove the old directory /_u_s_r/_l_i_b/_p_c_p/_p_m_n_s entirely, and re-install the PMNS for any optional PMDAs by running their _i_n_s_t_a_l_l scripts again (the procedure for doing this is covered in the last section of this chapter). If you are upgrading a Performance Co-Pilot 1.1 installation, the existing PMNS in /_u_s_r/_p_c_p/_p_m_n_s will be automatically relocated to /_v_a_r/_p_c_p/_p_m_n_s. In the unlikely event that this fails, you will need to re- install the PMNS for any optional PMDAs. If you are upgrading a Performance Co-Pilot installation, there may be some changes in the PMNS that have to be reconciled. If you end up with both of the files /_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t and /_v_a_r/_p_c_p/_p_m_n_s/_r_o_o_t._N, then the differences between the two files should be disjoint, resulting from a. changes to the base PMNS - these will likely be additions to _r_o_o_t._N that are not in _r_o_o_t, and b. additions to _r_o_o_t due to the local configuration of PMDAs. To update (or reconstruct) the PMNS, execute the following commands as rrrrooooooootttt: # cd /var/pcp/pmns - 15 - # : merge anything new from root.N into root # : ditto for any other .N files # ./Rebuild # rm -f root.N 2.10 _F_i_l_e_s__N_o_t__L_i_s_t_e_d__b_y_vvvveeeerrrrssssiiiioooonnnnssss If any of the optional Performance Metric Domain Agents (PMDAs) have been activated (i.e. installed from /_u_s_r/_p_c_p/_p_m_d_a_s) or customized PMDAs have been developed and installed, then files may have been added and/or modified in the following places. +o /_u_s_r/_p_c_p/_p_m_d_a_s - optional PMDAs are located in directories below here; the _I_n_s_t_a_l_l scripts may create executable binaries and/or help text files in these directories. +o /_v_a_r/_p_c_p/_l_i_b - files named _p_m_d_a_*._s_o are the access methods or daemons that implement the PMDA functionality within the Performance Metrics Collection System (PMCS). Some of these may have been installed by the PMDA _I_n_s_t_a_l_l scripts after the PCP images were installed with iiiinnnnsssstttt(1). +o /_v_a_r/_p_c_p/_p_m_n_s - any expansion of the Performance Metrics Name Space (PMNS) may cause new files to be added into this directory. +o /_v_a_r/_p_c_p/_c_o_n_f_i_g - assorted PMDAs and optionally configured PCP services are inclined to have configuration files below this directory that may be added or modified as part of their site-specific configuration after installation. +o /_v_a_r/_a_d_m/_p_c_p_l_o_g - the diagnostic logs from ppppmmmmccccdddd and PMDAs for a PCP collector configuration reside here. If ppppmmmmllllooooggggggggeeeerrrr instances are activated, it is most likely that the PCP archive log files will be created below here - one directory per logged host. +o /_v_a_r/_p_c_p/_T_u_t_o_r_i_a_l/_w_e_b_j_u_m_p_e_r._h_t_m_l - the indirect PPPPCCCCPPPPTTTTuuuuttttoooorrrriiiiaaaallll WebJumper from the PerfTools page of the Icon Catalog. 2.11 _O_t_h_e_r__I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n After installation has completed you should run the command showfiles -c -C -H pcp - 16 - This will list files that have been customized for your site that iiiinnnnsssstttt had a replacement for. Existing files moved aside will have a ....OOOO extension and new files that iiiinnnnsssstttt did not substitute for existing ones will have a ....NNNN extension. You must reconcile any differences between the files by hand. Several optional and example Performance Metric Domain Agents (PMDAs) are also shipped with the Performance Co- Pilot. These provide additional performance metrics and examples of PMDAs. The example and optional PMDAs and their associated source, configuration and executable files are located in subdirectories below /_u_s_r/_p_c_p/_p_m_d_a_s. In each directory you will find the following files. _R_E_A_D_M_E An overview of this PMDA, with particular reference to the range of performance metrics it supports, and any special installation directions. _I_n_s_t_a_l_l A ////bbbbiiiinnnn////sssshhhh script to install the PMDA and/or the associated PMNS components. The tasks performed by this script are fully described in the _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e Insight book. _R_e_m_o_v_e A ////bbbbiiiinnnn////sssshhhh script to reverse the tasks performed by _I_n_s_t_a_l_l. The tasks performed by this script are fully described in the _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e Insight book. other Assorted configuration files, C or C++ source, relocatable binaries, help text. Both _I_n_s_t_a_l_l and _R_e_m_o_v_e modify the contents of protected files and directories, and hence must be run as rrrrooooooootttt. The basic procedure you need to follow to configure an optional PMDA is set out below. You should, however, check the relevant _R_E_A_D_M_E file for any additional steps that may be required. PCP ccccoooolllllllleeeeccccttttoooorrrr systems For each system on which the optional metrics are to be collected do the following as rrrrooooooootttt: # cd /usr/pcp/pmdas/_P_M_D_A-_n_a_m_e # ./Install PCP mmmmoooonnnniiiittttoooorrrr systems As of PCP 2.0 the distributed PMNS means that it is - 17 - not necessary to perform any monitor-side installation to gain access to the metrics from any newly installed PMDA on a collector system. However some PMDAs also have monitor side components (e.g. _p_m_c_h_a_r_t views, _p_m_l_o_g_g_e_r configurations or special monitoring tools), and in some cases, these components are customized as a by-product of running the _I_n_s_t_a_l_l scripts. In these cases use the ----NNNN option to the _i_n_s_t_a_l_l script, i.e. do the following as rrrrooooooootttt: # cd /usr/pcp/pmdas/_P_M_D_A-_n_a_m_e # ./Install -N Finally, there is a HTML tutorial introduction to the Performance Co-Pilot, distributed in the _p_c_p._m_a_n._t_u_t_o_r_i_a_l subsystem. See the _R_E_A_D_M_E file in the directory /_v_a_r/_p_c_p/_T_u_t_o_r_i_a_l for instructions, or launch your Web browser with the URL ffffiiiilllleeee::::////vvvvaaaarrrr////ppppccccpppp////TTTTuuuuttttoooorrrriiiiaaaallll////iiiinnnnddddeeeexxxx....hhhhttttmmmmllll, or from the desktop, use the PPPPCCCCPPPPTTTTuuuuttttoooorrrriiiiaaaallll WebJumper in the PerfTools page of the Icon Catalog.